Added new endpoints and functionality #253
Open
+151
−25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1, would love for this to land. How many packets are stored? Are there cases where stations with long uptimes might not be able to handle responding to a request with a lot of packets? In that case, would it make sense to have a time query parameter - like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added two new endpoints (accessible only on the station's local network without any authentication):
/packets- for retrieving all received packets from the station as JSON;/radioBegin- for manual radio start (in case of automatic mode malfunction).Added option to send a custom radio message from the web dashboard (just by typing in the command box).
Improved display of received packets in the web dashboard (showing not only encoded but also decoded messages of received packets).